I forgot to mention, but the logic in these lines should be removed so that the tests ensure mrdocs is finding the appropriate include paths and to avoid including these paths twice.

https://github.com/cppalliance/mrdocs/blob/badb9d9e61ece24abf57efb261301eb290aaee2b/.github/workflows/ci.yml#L329C1-L340

I forgot to mention, but the logic in these lines should be removed so that the tests ensure mrdocs is finding the appropriate include paths and to avoid including these paths twice.

https://github.com/cppalliance/mrdocs/blob/badb9d9e61ece24abf57efb261301eb290aaee2b/.github/workflows/ci.yml#L329C1-L340

Done! removed

Looks great.

Now that I'm looking at Compiler.h/cpp, this looks kind of weird because it sounds like there are functions able to compile code. Maybe CompilerInfo.h/cpp? I'm just throwing ideas. I'm not sure. It's up to you.

I'm also a little worried about MSVC compiler identification, although this might work anyway as long as there's no "#include <...> search starts here:" in the MSVC output, which is kind of a way of identifying MSVC anyway.

These are just ideas. If you think it's good to go, then it's good to go.

I removed the MSVC detection (using filename) because it will fail when called with the arguments -v -E -x c++ - and as you said, the output will not contain the pattern we are looking for.

I also renamed Compiler.h/cpp -> CompilerInfo.h/cpp

Great! So this is good to go, right?

Have you checked the output in the CI artifacts? I don't want to merge two things in a row with problems in the output 😆

Please squash before you merge!

Have you checked the output in the CI artifacts? I don't want to merge two things in a row with problems in the output 😆

@alandefreitas @sdkrystian
I'm checking, I don't see any errors in the CI, it's passing Ok.
I understand that you want me to look at the entire output, but it seems strange to me that we are expecting a pattern in the output and it is not marked as an error. I mean maybe we have to modify the CI to make the error more obvious.
What pattern do you look for in the output to see if everything came out OK or not?
I would like to change the CI scripts in another PR, but I need help identifying the patterns.

@alandefreitas

I checked the output of the "Demos" job in Github Actions and everything seems fine

https://github.com/cppalliance/mrdocs/actions/runs/7262807028/job/19787446683?pr=515#logs